Skip to content

[CRE] OrgResolver with DB-backed cache - #23485

Open
bolekk wants to merge 2 commits into
developfrom
org_cache
Open

[CRE] OrgResolver with DB-backed cache#23485
bolekk wants to merge 2 commits into
developfrom
org_cache

Conversation

@bolekk

@bolekk bolekk commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

Use the caching OrgResolver implemented in smartcontractkit/chainlink-common#2342
Inject a DB-based cache. Enabled by default with a config flag to disable.

@github-actions

Copy link
Copy Markdown
Contributor

✅ No conflicts with other open PRs targeting develop

@bolekk
bolekk force-pushed the org_cache branch 2 times, most recently from 6dc7da5 to 4d79e91 Compare September 6, 2026 04:16
@bolekk bolekk changed the title [CRE] OrgResolver cache [CRE] OrgResolver with DB-backed cache Sep 6, 2026
@trunk-io

trunk-io Bot commented Sep 6, 2026

Copy link
Copy Markdown

Static BadgeStatic BadgeStatic Badge

View Full Report ↗︎Docs

@bolekk
bolekk force-pushed the org_cache branch 2 times, most recently from e3e706a to bf47f10 Compare September 6, 2026 15:10
@bolekk
bolekk marked this pull request as ready for review September 6, 2026 15:24
@bolekk
bolekk requested review from a team as code owners September 6, 2026 15:24
@bolekk
bolekk requested review from ibrajer, jmank88, patrickhuie19 and pavel-raykov and removed request for skudasov September 6, 2026 15:24
Comment thread core/config/docs/core.toml Outdated
# RequestTimeout bounds each organization lookup against the linking service.
RequestTimeout = '2s' # Default
# CacheEnabled turns on durable Postgres-backed caching of owner->orgID mappings.
CacheEnabled = true # Default

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: probably call it DurableCacheEnabled to underscore that the durable cache is enabled (the inmemory one is always on)

Comment thread .changeset/org-resolver-cache.md Outdated
"chainlink": minor
---

#added Durable caching of OrgResolver owner->orgID mappings (backed by Postgres, `CRE.Linking.CacheEnabled`, enabled by default).

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: can you update PR description / link JIRA to clarify why durable caching is needed.

pavel-raykov
pavel-raykov previously approved these changes Sep 7, 2026
Cache owner->orgID mappings in Postgres (CRE-5348). CacheEnabled now defaults to true. Requires chainlink-common with the merged caching OrgResolver refactor (#2342).
@cl-sonarqube-production

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants